fix(user_ldap): restore OCS API functionality for configID = '' - #63165
Merged
Conversation
The default in the past for a config prefix was '', changed to a default of s01 some year back. A refactor of the routes led to dropping the possibility of passing an empty config ID, breaking the administration interface for all users affected. Signed-off-by: Salvatore Martire <4652631+salmart-dev@users.noreply.github.com>
Contributor
Author
|
/backport to stable34 |
Contributor
Author
|
/backport to stable33 |
come-nc
approved these changes
Aug 13, 2026
Signed-off-by: Salvatore Martire <4652631+salmart-dev@users.noreply.github.com>
leftybournes
approved these changes
Aug 18, 2026
This was referenced Aug 18, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
LDAP configurations get a prefix in the form of
s01,s02, etc. This default in the past was ``. A refactor of the routes led to dropping the possibility of passing an empty config ID, breaking the administration interface for all users affected.Checklist
3. to review, feature component)stable32)AI (if applicable)